Cherry-pick of 198197d has failed:

On branch mergify/bp/8.17/pr-43106
Your branch is up to date with 'origin/8.17'.

You are currently cherry-picking commit 198197d02.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

Hmmm I thought the CI was failing due to flaky tests, but it seems that 8.17 and 8.16 backports are broken due to the libs bump.

https://buildkite.com/elastic/filebeat/builds/14865#01958fd4-32e6-4710-996d-cfcf2875f38e

It complains about two mapstr.M sharing the same backing map, which shouldn't happen. This is likely a guard to ensure m.Clone() always produce a new map.

I recall seeing similar failures before, but it was fixed in elastic/elastic-agent-libs#283 for v0.18.7. We require v0.18.9 here so this shouldn't happen. It is also weird that all the other backports are not failing on these tests. I'll keep digging.

This pull request has not been merged yet. Could you please review and merge it @khushijain21? 🙏

I found out why the tests broke with this PR, turns out it is not related to libs but to testify/assert. The bump to v1.10.0 includes a fix for NotSamef to fail if the values passed in are not pointers. This is already fixed in beats main.